[Snyk] Fix for 1 vulnerabilities#5360
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-10293725
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideThis PR updates specific backend dependencies by replacing workspace references with fixed version numbers to remediate a high-severity file access vulnerability in tarfs. Sequence Diagram: PR Handling for Snyk Dependency UpdatesequenceDiagram
participant SnykTool as "Snyk (Automated Tool)"
participant SourceRepo as "Source Repository"
actor Developer
SnykTool->>SourceRepo: Creates PR with updated 'package.json' (fixes SNYK-JS-TARFS-10293725)
SourceRepo-->>Developer: Notifies of PR
Developer->>SourceRepo: Pulls changes
opt Developer uses Yarn Zero-Installs
Developer->>Developer: Runs 'yarn' to update '.yarn/cache'
end
opt yarn.lock update failed during PR creation
Developer->>Developer: Manually updates 'yarn.lock'
end
Developer->>SourceRepo: Reviews changes
Developer->>SourceRepo: Merges PR
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
| "@backstage/backend-common": "0.24.1", | ||
| "@backstage/backend-plugin-api": "0.6.19", | ||
| "@backstage/config": "workspace:^", | ||
| "@backstage/config-loader": "workspace:^", | ||
| "@backstage/config-loader": "0.1.1", |
There was a problem hiding this comment.
Dependency Resolution Issue: Replacing workspace:^ references with specific npm versions breaks the monorepo's internal dependency structure. This change would cause the app to use external package versions rather than the local workspace packages, potentially introducing version mismatches and development workflow issues.
For addressing the vulnerability in tar-fs, the fix should be applied within the workspace packages themselves while maintaining the workspace:^ syntax. This preserves the monorepo's integrity while still addressing the security concern.
Consider reverting these changes to keep workspace:^ and instead update the vulnerable dependency in the appropriate workspace package.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/app-backend/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TARFS-10293725
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Upgrade backend dependencies to remediate a tarfs 'Link Following' vulnerability.
Bug Fixes:
Enhancements: